Thank you for looking into this. The CDN did sync, but it still has the old version of the file. The CDN copy is 1863 bytes, while our current file is 1953 bytes (ETag W/"6abf57ff-7a1"). The 90-byte difference is exactly the new line: { "/": "/syndromes/gastronomos-prosfora/*", "exclude": true }, Current state on our side (Oct 14, 07:50 UTC) Requesting https://www.kathimerini.gr/.well-known/apple-app-site-association with -A "AASA-Bot/1.0.0" returns: HTTP 200, Content-Type: application/json, no redirect ETag: W/"6abf57ff-7a1" (1953 bytes, includes the new line) cf-cache-status: DYNAMIC (Cloudflare is not caching this file; it is served directly from our origin) Earlier this week Cloudflare was returning a cached copy (cf-cache-status: HIT), which may explain the stale sync on Oct 13. That is no longer the case. Apple CDN (Oct 14, 06:59 UTC, Frankfurt edge) https://app-site-association.cdn-apple.com/a/v1/www.kathimerini.gr still returns: Content-Length: 1863 (old version, without the new line) Age: 3818 X-Cache: hit-stale, miss, hit-fresh, miss Questions Could you check whether your crawler's latest attempts to fetch our file are succeeding? The hit-stale suggests the CDN is still serving the old copy while a re-fetch is pending or failing. Now that our origin serves the correct file without caching, is there a way to trigger a re-sync, or should we wait for the next scheduled one? Regarding the apex domain: our app currently uses only applinks:www.kathimerini.gr. If we serve the file directly on kathimerini.gr, do we also need to add applinks:kathimerini.gr to the entitlements in a new app release? Thanks again for your help.